An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API. Affected accounts: Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously. API errors observed When calling PATCH /v1/appStoreVersions/{id}/relationships/build: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state." What I have verified All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue Question Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page? I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.

Hi all, Looking for some clarity.. I have an app (Pocket Love: AI Roleplay Chat, Apple ID: 6745031268) that went through a long review process with many resubmissions. The feedback I received across those reviews was often generic “overtly sexual”) message, but without any detail on exactly what needed to change. Because of that, I approached it iteratively making adjustments each time based on what I thought the issue might be. Over time I made quite significant changes across the app (imagery, unlockable content, voice-overs, menus, copy, etc.), and increased the age rating to 18+. I also had a call with a policy eexpert & App Review. In the final interaction, I was asked to ensure all unlockable content was visible, so I re-uploaded a build and provided screenshots with everything pre-unlocked for transparency. Despite this, my account has now been flagged under 3.2(f) for “dishonest or fraudulent activity,” and is pending termination. What I’m struggling to understand is: Can repeated resubmissions / iterative changes alone be interpreted as “evasion” under 3.2(f)? Or does this typically mean App Review believes there was something intentionally misleading? From my perspective, I was trying to respond to feedback and get the app into a compliant state, not bypass review or hide anything. The game does have "sexy" imagery lingerie etc..and adult themes but 0 nudity and is tamer than similar games live on the app store. Would really appreciate any insight from others who’ve experienced similar, or from anyone familiar with how this is interpreted internally. I can't believe my account is pending termination without any intentional wrongdoing, I currently have 3 other live games one with strong revenue, that will be removed too due to this. My initial appeal was rejected today. Thanks!

My app was declined for violation of Guideline 5.1.1. I'm very confused though, because a shopping app like Nike is permitted to not allow anyone into their app if they don't "Sign Up/Log In", yet my client a smaller first time app maker, isn't allowed to do the same? Why is it okay for a company like Nike to do it but not smaller brands?

I had an app rejected for a reason I thought was incorrect. I replied with an explanation and resubmitted, but it was rejected again, so I clicked the link to appeal that went to the link below where I submitted a detailed appeal.https://developer.apple.com/contact/app-store/?topic=appealI did not receive any email confirmation or response from the appeal and can find now way to track the status of the appeal. However, I do now see in iTunes Connect that the app no loger displays the red bar at the top that used to say "There are one or more issues with the following platform(s):1 unresolved iOS issue". Does this mean the appeal was accepted? Is there a way to track the status of an appeal?

Hi everyone, I am writing this post with the hope that someone from Apple's App Review team, Developer Relations, or the wider developer community can shed some light on what I am experiencing. I have exhausted every official support channel available to me, and I am at a complete loss. ━━━━━━━━━━━━━━━━━━━━━━━ THE SITUATION ━━━━━━━━━━━━━━━━━━━━━━━ I have a v1.0 iOS app that has been stuck in 'Waiting for Review' for 57 days. It has never progressed beyond this status. No rejection. No feedback. No communication. Just silence. I am not here to complain. I am here because I genuinely do not understand what is happening, and I need guidance. ━━━━━━━━━━━━━━━━━━━━━━━ TIMELINE ━━━━━━━━━━━━━━━━━━━━━━━ • Day 1 — App submitted for review. Status: 'Waiting for Review.' • Day 22 — No movement. No feedback. Out of frustration, I made the mistake of doing a Developer Reject and resubmitting. I now understand this was the wrong decision, as it likely reset my position in the queue. • Day 27 — Contacted Apple Developer Support. A Senior Advisor confirmed the app was still in review and said they would reach out to the internal review team. • Day 42 — Still no change. Sent a formal follow-up and escalation request. • Day 44 — A second Senior Advisor responded, confirming they had also forwarded the case to the review team. • Day 57 (today) — The app is still in 'Waiting for Review.' Nothing has changed. Two separate Senior Advisors have each told me they contacted the internal review team. After both of those interactions, nothing changed. ━━━━━━━━━━━━━━━━━━━━━━━ WHAT MAKES THIS UNUSUAL ━━━━━━━━━━━━━━━━━━━━━━━ I want to be clear about something: the app has NEVER entered 'In Review.' It has been in 'Waiting for Review' the entire time. This is not a case of a slow review — it appears the app has never been picked up for review at all. I have checked Apple's System Status page multiple times throughout these 57 days. All services have consistently shown as fully operational. I have not resubmitted again after Day 22. I have been patiently waiting, following the advice given to me. ━━━━━━━━━━━━━━━━━━━━━━━ MY HONEST QUESTIONS ━━━━━━━━━━━━━━━━━━━━━━━ Is it technically possible for a v1.0 app to be permanently stuck in 'Waiting for Review' without any notification or rejection? Could this be a system or queue issue on Apple's end? Is 'Waiting for Review' for 57 days — with no status change and no communication — within the range of what other developers have experienced? I want to understand if this is abnormal. When a Senior Advisor says they have 'forwarded the case to the review team,' what does that actually mean in practice? Is there a way to verify this happened or to escalate further? Is there a formal escalation path beyond Developer Support — for example, Developer Relations or the App Review Board — for situations where standard support channels have not produced any result after nearly two months? Could the app category (social / matching) be the reason for an extended manual review? If Apple requires additional information, documentation, or content moderation policies from developers in certain categories, why is there no notification or communication mechanism to request this? ━━━━━━━━━━━━━━━━━━━━━━━ WHAT I AM NOT ASKING FOR ━━━━━━━━━━━━━━━━━━━━━━━ I am not asking for my app to bypass the review process. I am not asking to skip the queue. I am not asking for guaranteed approval. I understand Apple's review process exists to protect users, and I fully respect that. I am simply asking for ONE of two things: — Either: review the app and give me a decision — approval or rejection, both are acceptable. — Or: tell me if there is a problem, a hold, or something you need from me, so I can act on it. Fifty-seven days of silence, with no path forward, is the one outcome I cannot work with. ━━━━━━━━━━━━━━━━━━━━━━━ A NOTE TO APPLE DEVELOPER RELATIONS ━━━━━━━━━━━━━━━━━━━━━━━ If anyone from Apple is reading this — I am not writing out of anger. I am writing because I am a solo developer who has poured everything into this product, and I am genuinely stuck. I have done everything I was asked to do. I have been patient. I have followed the process. All I am asking for is a resolution — in any direction. If there is anything I can provide — demo account credentials, additional documentation, a content moderation policy, privacy details, anything at all — I will provide it within hours of being asked. Thank you sincerely to anyone who takes the time to read this and share their experience or advice. — Akif Solo Developer

Our app update for Underground Arena (a padel sports community platform) has been pending review for over (65 days), since the first submission on February 11, 2026. At no point has the submission transitioned to "In Review" or received any feedback. The previously approved version (v1.1.2) was reviewed and approved within one day. This update includes security improvements, privacy policy alignment, and metadata updates. No changes to monetization or permissions. We have submitted two expedited review requests and opened support case 102840575585 — none have resulted in movement. We have a padel tournament on April 22, 2026 that requires the updated app for participant registration. Our Android version is already live on Google Play, and iOS users are currently unable to access the latest features. Could someone from the review team please confirm whether this submission is in extended review, or advise on any information needed to proceed? Thank you.

Hello, Our app has been stuck in "In Review" for 7 days, after being approved. The iOS version was approved on April 9th and the macOS version was approved on April 12th. Since then, both versions show "In Review" and there has been no status changes or messages in App Store Connect. • April 8 ---> Waiting for Review • April 9 ---> In Review (Approved) • ... • April 16 ---> In Review We contacted Apple a week ago (case ids 102865508515 and 102865870578) but there was no response. We also talked to Apple Support, they told us the issue has been escalated to the technical team. There are also leaderboards that were archived before these last versions and they are still showing in the Games App and Game Center. Possibly because of this same issue, we suspect. At this point we don't know what the issue is, how long until these very important updates will go live, or when we can push other updates. App ID: 1611398578 Thanks.

Hello Team, We’ve confirmed Apple’s current minimum OS requirements for Xcode 26: iOS 15 – 26 iPadOS 15 – 26 tvOS 15 – 26 watchOS 8 – 26 visionOS 1 – 26 macOS 11 – 26 Are we correct in understanding that any builds targeting below these versions are no longer accepted by the App Store and may fail to launch for users on older systems? Like this https://developer.apple.com/forums/thread/821370?answerId=882822022#882822022 For Steam macOS distribution, can older macOS targets still be supported, or should we align strictly with Apple’s minimums? Thank you and best regards, Phong

Hello, I'm the developer of RPGPlayer, a game emulator for RPG Maker games that has been live on the App Store since 2025. I'm writing here out of frustration and desperation after 2+ months of trying to publish a critical bug fix update. The Situation I submitted v2.4 on February 21, 2026. Since then, I have received 9+ rejections under Guidelines 4.7 and 2.5.2. Every single rejection message is word-for-word identical — the same copy-pasted text, every time. None of my detailed technical responses have ever been acknowledged or addressed. I have submitted appeals twice through the App Review Board. Both times I received the same automated response: "The App Review Board will contact you directly once they've completed their investigation." The first appeal went unanswered for over 30 days. At this point, I genuinely do not believe a human being has opened my app during any of these reviews. The Technical Reality RPGPlayer is a game emulator, explicitly permitted under Guideline 4.7. The rejection under 4.7 states that "HTML5-based games appear to be an incidental feature." This is incorrect. RPG Maker MV/MZ games are built on HTML5/JavaScript by design — that is the engine's native architecture on all platforms including PC and consoles. The WKWebView is the emulation layer, not a web browser or game portal. There are zero bundled games. The rejection under 2.5.2 states the app "installed or launched executable code." The app does not download anything from the internet. It includes a bundled, statically-linked runtime (MKXP-Z) that interprets local game scripts from user-imported files — identical to how Delta Emulator interprets ROM instructions. The Double Standard Other apps on the App Store use the exact same architecture as RPGPlayer: Delta Emulator — approved under Guideline 4.7, interprets user-provided ROM files Quest Play — RPG Maker MV/MZ player, uses the same WebView approach, currently receiving updates ArkRPG — same engine, same architecture, also on the App Store and getting updates. These apps are approved and actively updated. RPGPlayer is being rejected with automated messages for doing the exact same thing. What I've Tried Detailed technical responses in Resolution Center — ignored Two App Review Board appeals — no meaningful response Contact Us support requests — automated replies Provided ROM files, video walkthroughs, and thorough App Review Notes — none of it acknowledged The Impact My users have been waiting 50+ days for a critical bug fix. Some have left negative reviews calling me a scammer because they think I abandoned the app. I haven't. I've been fighting this review process every single day. I have a Meet with Apple appointment scheduled. But I wanted to share this here as well — both to ask if anyone has faced a similar situation with emulator apps, and to document what is happening in case it helps other developers. Has anyone successfully resolved a 4.7 + 2.5.2 rejection for a legitimate emulator app? Any advice is welcome.

Hi everyone, I am hoping someone here has experienced this and can help, because we are in a really difficult position right now. We received a notice from App Review regarding Guideline 5.6.4 and have been working hard to prepare a full response with supporting evidence. The problem is that a draft response exists in App Store Connect that we cannot submit or delete. Every time we click either Submit or Delete Draft, we get the same error: "The resource cannot be found" That is it. No further explanation, no workaround, nothing. The draft is just stuck there and we cannot get past it. Because we could not submit through the normal channel, we uploaded a new build with our action plan included in the notes, hoping that would reach the review team. The build has been sitting there unreviewed. We have raised a support ticket with Apple Developer Support and have not received any response. The clock is ticking. App Review has given us a deadline to respond or face removal from the App Store. We have our response ready. We have our evidence ready. We just physically cannot submit it because of what appears to be a technical bug on Apple's side. Has anyone else hit this "resource cannot be found" error on a draft App Review response? Is there any other channel we can use to get this in front of the App Review team directly? We have tried everything we can think of. Any help would be massively appreciated. This is our livelihood and the deadline pressure combined with a broken system is genuinely distressing. Thank you

Hello, I need guidance on App Store Connect product state vs StoreKit behavior during App Review. Stack: iOS app (Expo / React Native), subscriptions via RevenueCat + StoreKit. Bundle ID matches App Store Connect. RevenueCat API keys — what I’ve verified locally: With the production RevenueCat API key (iOS appl_..., same as the submitted build), everything works on local device but not when I download it from TestFlight. I have also tested with RevenueCat’s sandbox / test API key (the separate key intended for sandbox/testing). That setup works as well — I can load offerings and complete test purchases the same way What RevenueCat (SDK / dashboard health) reports: Product monthly is configured in RevenueCat. Warnings that products aren’t approved in App Store Connect yet and that the default offering has configuration issues. Apple’s product state: WAITING_FOR_REVIEW. The SDK still states that test purchases are possible. What App Review reports: After onboarding a new business account, “Activate subscription” leads to an error (plans don’t load / purchase path fails). Review suggested an app code issue. Why this is confusing: Locally, both RevenueCat key modes I tried (production and sandbox/test) work with Apple Sandbox on the device. The submitted build uses the production RevenueCat key. Review still sees a failure. Questions: For IAP in WAITING_FOR_REVIEW, should App Review always use an Apple Sandbox account to test subscriptions until the product is fully approved? Is it documented that StoreKit may not return products during review without Sandbox while the product remains WAITING_FOR_REVIEW? Has anyone else seen “works locally (prod + sandbox RevenueCat keys + Apple Sandbox) but Review fails” with the same WAITING_FOR_REVIEW state? Thanks for any official documentation or similar threads.

Hello, I have a perplexing issue with apple reviewers not having the same experience as myself regarding the paywall. This is an Expo app and uses RevenueCat and SuperWall integrations. This app is going through its first review - it is not published yet. So the app and its subscriptions are being reviewed for the first time. I should also mention that this is my first time as an app developer, so please pardon my ignorance. When I install the app from TestFlight and launch it, I see the paywall with the product prices shown and I can complete a test purchase. Same for my friends who I've asked to test for me. But the apple reviewer does not see the product prices when the paywall is shown to them. Without being able to replicate the problem I am flying blind. I don't want to re-submit the app for review only to find the same problem exists. I also need to understand what is different between my testing environment and the apple testers. If anyone can point me in the right direction here I would really appreciate the help!

I’m trying to submit my app for review, but I’m currently blocked due to a recurring issue with in-app subscriptions. Both of my auto-renewable subscriptions (premium_monthly and premium_yearly) are marked as “Waiting for Review”. However, I am still seeing the blue box stating that “your first subscription must be submitted with a new app version.” Despite creating a new version (1.0.1) and uploading/selecting a new build , I am not seeing the “In-App Purchases and Subscriptions” section on the version page, and I therefore cannot link the subscriptions before submitting. This issue is blocking my ability to submit the app for review. Any help to resolve this would be greatly appreciated.

Hi there, I originally submitted my app on February 3, 2026. It was rejected initially with a request for additional information. Since then, I’ve gone through several rounds of communication and provided all the requested documents, including company formation details etc. The app was moved to “In Review” again on March 10, 2026, but there has been no update since then. It’s now been over two months since the initial submission, and I haven’t received any further feedback or decision since more than a month. This delay is starting to impact our business, as we’ve been waiting without any clear timeline or direction. Could you please advise if there’s any way to contact the review team directly or expedite the process or any other suggestion that could help? Thank you.

Since April 6 I’m waiting for review. No updates. They usually say that takes 24-48hrs to be reviewed. I'm at 10 days already. And I get no response on my emails and ticket.

Hi everyone, I'm developing a music streaming app for iOS and I have a question about App Store guidelines before I submit. Here's how my app works: The app has a signup screen and a login screen There are NO in-app purchases at all Users pay for their subscription on our external website (a separate web app) Once they've paid on the website, they log into the iOS app to listen to music The app itself contains no payment flow, just an external link directing users to our website to subscribe My company is based in France (EU/EEA). My questions: Is this external-payment-only model permitted under current App Store Review Guidelines? Since I'm in the EEA, do I need to apply for an External Purchase Link Entitlement (StoreKit External Purchase Link), or can I operate without it since payment happens entirely outside the app? Is there a difference between simply not having any payment in the app vs. actively linking users out to a website for payment? I want to get this right before submitting. Any guidance from Apple engineers or developers who've dealt with this would be really appreciated. Thanks!

Hello everyone, I’m facing an issue with my app "FindUWay" (iOS), and I’m trying to understand if this is related to EU Digital Services Act (DSA) compliance. Current situation: App is approved and published on the App Store All agreements, tax forms (including W-8BEN), and banking info are completed and active App is set to be available in 175 countries, including Malta Issue: The app is NOT available in Malta and shows "App Not Available" on multiple iPhones and Apple IDs. Important detail: In App Store Connect, the only pending item is: Digital Services Act (DSA) compliance → Status: "In Review" since April 5th What I’ve observed: The app works and appears normally in some regions In Malta (EU), it does not open or install properly This seems to affect multiple devices (including iPhone 17 Pro Max) Questions: Is DSA compliance review blocking app availability in EU countries? Is it expected for the app to be unavailable while DSA is still "In Review"? Is there anything else I need to configure or submit? Has anyone experienced delays with DSA review recently? This is impacting my app launch, so any help or insight would be greatly appreciated. Thank you!

Hello, I have a question regarding Apple's policy on third-party SDK signatures. I have reviewed the official documentation here: https://developer.apple.com/support/third-party-SDK-requirements/ Our app is developed in the following environment: Minimum Target: iOS 15 Xcode: 26.2 Engine: Unreal Engine 4.27.2 We are integrating the Firebase SDK into our project. However, we are experiencing app crashes caused by an issue within the GoogleAdsOnDeviceConversion.xcframework included in the Firebase SDK (related to a memory optimization issue in UE4). According to an official response from the Firebase team, this crash can be resolved by wrapping the Firebase SDK in a dynamic XCFramework. We have confirmed that this solution does indeed fix the crash. The problem is that wrapping the Firebase SDK in a custom dynamic XCFramework removes all of the original Firebase SDK signatures. The documentation on third-party SDK signatures, which I referenced earlier, states that a signature is required for the Firebase SDK, and this requirement also applies when repackaging it. This leads me to the following questions: Question 1: When we wrap and repackage the Firebase SDK, is it mandatory for the resulting XCFramework to still include the original Google LLC signature? Question 2: To resolve the crash, we intend to use the Firebase SDK by wrapping it in our own dynamic XCFramework (e.g., FirebaseWrapper.xcframework). When we do this, the resulting XCFramework loses the Google LLC signature, and consequently, the final built IPA's signature list does not contain any Firebase-related signatures. Will this be a reason for rejection during App Store review? Question 3: If we wrap the Firebase SDK in a dynamic XCFramework and then sign it with our own developer certificate, would this be a reason for rejection during App Store review?

Hello everyone, I’m facing a persistent App Store rejection under Guideline 2.1(b) – App Completeness, related to In-App Purchases, and I’m unable to reproduce the issue on my end. Issue reported by Apple Review Apple Review team reports: “No action occurred when we attempted to buy the subscription.” Device: iPad Air 11-inch (M3) OS: iPadOS 26.4.1 What I have verified from my side I have thoroughly tested the subscription flow under multiple scenarios: Sandbox Testing Using sandbox test accounts Product loads correctly Purchase flow completes successfully Apple payment sheet appears properly TestFlight Testing Installed app via TestFlight Logged in with real Apple ID (Beta tester) Successfully completed subscription purchase Device Testing Tested on multiple iPhones Tested on iPad as well Purchase flow works correctly on all devices App Store Connect Configuration Paid Apps Agreement → Active Banking & Tax → Completed (no pending warnings) In-App Purchase status → “In Review” Product is correctly configured and attached to app What Apple is experiencing Based on their feedback and screenshots: Subscription screen loads correctly Product price is visible When tapping “Subscribe Now” → no action occurs No error message, no purchase sheet Is there a recommended workaround or reviewer instruction to avoid this deadlock? Any insights or real-world experience would be greatly appreciated. Thanks in advance.

Dear Developer, We are writing to notify you that the Ministry of Industry and Information Technology (MIIT) has identified your app as in violation of the Regulation on Personal Information in Mobile Apps. If your app is not compliant by April 20, 2026, MIIT will find your app to be illegal in China, and demand that Apple remove it from the China App Store. The App Review Guidelines require apps to comply with all legal requirements in any location where they are offered. Legal Apps must comply with all legal requirements in any location where you make them available (if you’re not sure, check with a lawyer). We know this stuff is complicated, but it is your responsibility to understand and make sure your app conforms with all local laws, not just the guidelines below. And of course, apps that solicit, promote, or encourage criminal or clearly reckless behavior will be rejected. We ask that you refer to the directions included in the document attached to this message. If you have any questions, we advise you to get in touch with MIIT within 24 hours of this notice by submitting your feedback via https://app.caict.ac.cn/. Thank you for your prompt attention to this matter. Best regards, App Review Message Attachments: Directions.docx